Parley Deck Skill

by Feci

Free Download 1 Visit Website

Versions:

  • 2.11.0
  • 2.10.0
  • 2.9.0
  • 2.5.1
  • 2.5.0
  • 2.4.0
  • 2.3.0
  • 2.2.0
  • 2.1.0
  • 1.5.0
  • 1.4.6
  • 1.4.5
  • 1.4.4
  • 1.4.3
  • 1.4.0
  • 1.3.5
  • 1.3.4
  • 1.3.3
  • 1.3.2
  • 1.3.1
  • 1.2.0
  • 1.1.0
  • 1.0.4

Parley Deck Skill, published by Feci, is an installer for the Parley Deck multi-agent cooperation skill, falling within the developer tooling and AI-assisted software collaboration category. Its purpose is to install the vendor-neutral Parley Deck AI cooperation skill into a range of supported environments, namely Codex, Claude Code, zcode, Antigravity CLI, Hermes, Kimi Code, or a custom skill directory, making it useful for teams that coordinate proposals across multiple AI coding agents and need a consistent, shared cooperation protocol regardless of the underlying tool. The project has shipped 23 versions to date, and the current release is version 2.11.0. This release adds an "Existing alternatives" section to the round-1 participant template, together with the instruction that the command-line tool now enforces. Under this rule, a participant enumerates the mechanisms a proposal builds by hand and, for each one, names what the toolchain, standard library, dependencies, or platform already ships, marking every load-bearing element as either forced by a constraint or merely inherited. A scoped null result is legal, provided it names the sources consulted. The change closes a drift between the two halves of the project and introduces a cross-version compatibility consideration: Parley Deck CLI 1.47.0 rejects a round-1 artifact whose section is missing or empty, so any skill older than this one produces work the tool refuses. Users running the current CLI therefore need this version of the skill or newer for their round-1 output to be accepted. The bundled protocol snapshot in 2.11.0 carries the matching unconditional section and the corrected per-track binding row, keeping the third copy of the protocol in step with the two copies that the drift guard covers. This third copy went stale twice during the change because nothing currently checks that the two repositories move together, a gap the release documentation highlights as a known maintenance risk for the project going forward.

Tags: